home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
EnigmA Amiga Run 1996 June
/
EnigmA AMIGA RUN 08 (1996)(G.R. Edizioni)(IT)[!][issue 1996-06][EARSAN CD VII].iso
/
earcd
/
texts
/
hsc.lha
/
hsc
/
src_docs
/
questions.hsc
< prev
next >
Wrap
Text File
|
1995-12-06
|
2KB
|
68 lines
<WEBPAGE chapter="hsc - " title="Questions & Answers"
PREV="messages.html"
NEXT="bugs.html">
<$MACRO QUEST NAME:string>
<$if (SET NAME)>
<A NAME=(Name)>
</$if>
<STRONG>Q: </STRONG>
<$if (SET Name)>
</A>
</$if>
</$MACRO>
<$MACRO ANSWR>
<BR><STRONG>A: </STRONG>
</$MACRO>
<QUEST NAME="uri">Why do You call it URI? I thought it's URL (<EM>Universal Resource
Locator</EM> or <EM>U R lost</EM>)?
<ANSWR>Ok, put a finger into your mouth and try to reach as far inside
as possible. After some specific point, you will empty your stomach.
And what do you say then? Exactly, "<STRONG>URL</STRONG>"! So the main
reason why I do not like the term URL is because it always reminds me
of puking.<BR>
Additionally, the Internet-Draft for HTML 2.0, June 16, 1995, tells
you:
<PRE>
URI
A Universal Resource Identifier is a formatted string
that serves as an identifier for a resource, typically
on the Internet. URIs are used in HTML to identify the
destination of hyperlinks. URIs in common practice
include Uniform Resource Locators (URLs)[URL] and
Relative URLs [RELURL].
</PRE>
I really like that term URI a lot more. Altough, I've never really understood
what's the difference between URL and URI. But who cares anyway?
<P>
<QUEST NAME="jerk">What are jerks?
<ANSWR>Jerks are persons suffered by a well-known desease called
<EM>Netscapissm</EM>. Their sources contain sections like
<PRE>
<TG>BODY BGCOLOR=#123456</TG>
<TG>BLINK</TG>Click here!<TG>/BLINK</TG>
</PRE>
But, not all jerks became jerks because they like to be a jerk. Very often,
jerks are forced to use code as seen above by their employee.
<P>
<QUEST>Why is <hsc> that slow?
<ANSWR>One reason is, that <hsc> handles (nearly) all resources dynamically
(That means, it often calls <CODE>malloc()</CODE> and <CODE>free()</CODE>,
which are known to be quite slow).<BR>
Another, quite embarrasing, reason is, that most of these resources are
kept in linked lists. And therefor, if <hsc> has to look for something, it
sequentially searches these list. Shame on me, I should use an AVL-tree for
such things!
<P>
</WEBPAGE>